Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Return debuggable CAS errors on consul state put into v1.5 #33457

Closed
wants to merge 1 commit into from

Conversation

teamterraform
Copy link
Contributor

Backport

This PR is auto-generated from #33108 to be assessed for backporting due to the inclusion of the label 1.5-backport.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


Ran into this error while running terraform inside a container, after it applied my plans, terraform failed saving state to Consul. I suspect my policy needs tweaking, but it's near impossible to tell with an error like this:

╷
│ Error: Failed to save state
│ 
│ Error saving state: consul CAS failed with transaction errors:
│ [0xc0006e93c8]
╵

This PR changes the the rendering of the error instance to actually print the message, instead of the memory address of said error instance.

Target Release

1.15.x

Draft CHANGELOG entry

BUG FIXES

  • When using consul as a state backend and failing to save state, consul CAS failed with transaction errors no longer shows an error instance memory address but an actual error message.

@teamterraform teamterraform requested a review from a team as a code owner June 30, 2023 13:50
@teamterraform teamterraform force-pushed the backport/patch-1/formerly-fluent-mallard branch 3 times, most recently from 2631b56 to 67fbeef Compare June 30, 2023 13:50
@alisdair alisdair closed this Jun 30, 2023
@alisdair alisdair deleted the backport/patch-1/formerly-fluent-mallard branch June 30, 2023 16:02
Copy link
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants